Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 7dbf92836bbf9f2fa9b4ffda3a22413170efeac3cec5a083d52b4af8902a0571

Tx prefix hash: bd98356721b1cb429e5c2b83d8735c1a8e28e50a78d5705805bcae69b88983f7
Tx public key: 19df1c8a402c70697142c0757573f9c20fb753df1d3a9823d86e6dba7eddc555
Timestamp: 1710659299 Timestamp [UCT]: 2024-03-17 07:08:19 Age [y:d:h:m:s]: 01:091:00:40:20
Block: 980137 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 325961 RingCT/type: yes/0
Extra: 0119df1c8a402c70697142c0757573f9c20fb753df1d3a9823d86e6dba7eddc55502110000000d59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a5cdddc1a0192bf6ff67995e0a4d6279d8af56ee5d93309df0537d1d85d0e5d 0.600000000000 1440196 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 980147, "vin": [ { "gen": { "height": 980137 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a5cdddc1a0192bf6ff67995e0a4d6279d8af56ee5d93309df0537d1d85d0e5d" } } ], "extra": [ 1, 25, 223, 28, 138, 64, 44, 112, 105, 113, 66, 192, 117, 117, 115, 249, 194, 15, 183, 83, 223, 29, 58, 152, 35, 216, 110, 109, 186, 126, 221, 197, 85, 2, 17, 0, 0, 0, 13, 89, 218, 211, 245, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8