Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 997c1cefda1af1dbda9d607aac7a0b1663f0cb2e10d2232fe04d799db20e47b3

Tx prefix hash: 93ff3430b8c4cf3605492388f90b5314daf4ea83b84c722bdca493edbc7ffacb
Tx public key: bf4d709a46a7489d8ffc3aafb019abbb668b0c576443cf3849f4313e0766a763
Timestamp: 1712424973 Timestamp [UCT]: 2024-04-06 17:36:13 Age [y:d:h:m:s]: 01:243:21:25:35
Block: 994719 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 433048 RingCT/type: yes/0
Extra: 01bf4d709a46a7489d8ffc3aafb019abbb668b0c576443cf3849f4313e0766a7630211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b4bae51b74b72a36f36f3c4d5cc6455809ff1bb3dabb26813808b9d049f6bee1 0.600000000000 1455123 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": 994729, "vin": [ { "gen": { "height": 994719 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b4bae51b74b72a36f36f3c4d5cc6455809ff1bb3dabb26813808b9d049f6bee1" } } ], "extra": [ 1, 191, 77, 112, 154, 70, 167, 72, 157, 143, 252, 58, 175, 176, 25, 171, 187, 102, 139, 12, 87, 100, 67, 207, 56, 73, 244, 49, 62, 7, 102, 167, 99, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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