Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7038951743be9afe5d79b586406bb38c7c1df598281e57acf5fcbbebcd200a1c

Tx prefix hash: 59442ea3a65090a53dd1b48f66c6fa9e82c003be317ceb5fe36b37e5d826b706
Tx public key: ceb62713f2eac4865743b3eda5cfc2aa2bf8f10d9c3c29b8428c143e2d26fb4c
Timestamp: 1696907267 Timestamp [UCT]: 2023-10-10 03:07:47 Age [y:d:h:m:s]: 01:140:21:16:36
Block: 866311 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 361688 RingCT/type: yes/0
Extra: 01ceb62713f2eac4865743b3eda5cfc2aa2bf8f10d9c3c29b8428c143e2d26fb4c021100000002faf35c9c000000000000000000

1 output(s) for total of 0.827088661000 dcy

stealth address amount amount idx
00: 0e4e1ff8536c14c6507999a5b6b40bc7b07e7977783a8286e7f3c8c97fb58e4b 0.827088661000 1320891 of 0

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": 866321, "vin": [ { "gen": { "height": 866311 } } ], "vout": [ { "amount": 827088661, "target": { "key": "0e4e1ff8536c14c6507999a5b6b40bc7b07e7977783a8286e7f3c8c97fb58e4b" } } ], "extra": [ 1, 206, 182, 39, 19, 242, 234, 196, 134, 87, 67, 179, 237, 165, 207, 194, 170, 43, 248, 241, 13, 156, 60, 41, 184, 66, 140, 20, 62, 45, 38, 251, 76, 2, 17, 0, 0, 0, 2, 250, 243, 92, 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