Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6d439c61973471248bbc4714d063ff1cc42205adef704f8afe9ba2ee9f5c6b0c

Tx prefix hash: 281a09157f91d5128302c49d79dc8e8c7c1cafe76f7fafec68a0637e97ef7c54
Tx public key: a67311d28897277c92a05991066e475593fabe1fe083b018ec1e0cbe3196cf3c
Timestamp: 1702423234 Timestamp [UCT]: 2023-12-12 23:20:34 Age [y:d:h:m:s]: 01:330:20:04:43
Block: 911854 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 495285 RingCT/type: yes/0
Extra: 01a67311d28897277c92a05991066e475593fabe1fe083b018ec1e0cbe3196cf3c02110000000ae6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 95913cacbd90b66f1d1d1a14f023dff3c3b83f6a1b539337ad8d7e02e7c0330c 0.600000000000 1369070 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": 911864, "vin": [ { "gen": { "height": 911854 } } ], "vout": [ { "amount": 600000000, "target": { "key": "95913cacbd90b66f1d1d1a14f023dff3c3b83f6a1b539337ad8d7e02e7c0330c" } } ], "extra": [ 1, 166, 115, 17, 210, 136, 151, 39, 124, 146, 160, 89, 145, 6, 110, 71, 85, 147, 250, 190, 31, 224, 131, 176, 24, 236, 30, 12, 190, 49, 150, 207, 60, 2, 17, 0, 0, 0, 10, 230, 210, 127, 156, 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