Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 06e73ffa65ad87ffdf8e72737fb7835f3e94711e00334deada3d8e88106f3ea3

Tx prefix hash: 3b9bc3c42dc7fa819caf44e8e774e369298234d3ef3073bbdfcca7532b799eed
Tx public key: 1855abdf99814a1f6aea82637548eb05c46d415e2ad8b214cebdbd9d87a8f2e7
Timestamp: 1705379679 Timestamp [UCT]: 2024-01-16 04:34:39 Age [y:d:h:m:s]: 01:153:16:57:15
Block: 936323 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 370884 RingCT/type: yes/0
Extra: 011855abdf99814a1f6aea82637548eb05c46d415e2ad8b214cebdbd9d87a8f2e70211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 88eb7b260d165a165dcef6f3f428b7df3fe7407c53b07a7e5b1a945d88758b5f 0.600000000000 1394347 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": 936333, "vin": [ { "gen": { "height": 936323 } } ], "vout": [ { "amount": 600000000, "target": { "key": "88eb7b260d165a165dcef6f3f428b7df3fe7407c53b07a7e5b1a945d88758b5f" } } ], "extra": [ 1, 24, 85, 171, 223, 153, 129, 74, 31, 106, 234, 130, 99, 117, 72, 235, 5, 196, 109, 65, 94, 42, 216, 178, 20, 206, 189, 189, 157, 135, 168, 242, 231, 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