Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b5cd0dd78786eb410095b2cde8d192858d52c00a66d24168b4a2a83ed574cf2

Tx prefix hash: cceb08f6583a07e0f3c123fe36e46b08d225e0882ad9cc474a21a74316beb220
Tx public key: 702188005e3d2befac542b7a576e0b2fa7ce481226b19a47e5d7d32828d1d124
Timestamp: 1715204166 Timestamp [UCT]: 2024-05-08 21:36:06 Age [y:d:h:m:s]: 00:263:01:47:59
Block: 1017807 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 188104 RingCT/type: yes/0
Extra: 01702188005e3d2befac542b7a576e0b2fa7ce481226b19a47e5d7d32828d1d1240211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7bb1fbc72e53d1aea3b4d89b28154b3e64aea6b0add68161af0f6fa52fa77dc2 0.600000000000 1481592 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": 1017817, "vin": [ { "gen": { "height": 1017807 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7bb1fbc72e53d1aea3b4d89b28154b3e64aea6b0add68161af0f6fa52fa77dc2" } } ], "extra": [ 1, 112, 33, 136, 0, 94, 61, 43, 239, 172, 84, 43, 122, 87, 110, 11, 47, 167, 206, 72, 18, 38, 177, 154, 71, 229, 215, 211, 40, 40, 209, 209, 36, 2, 17, 0, 0, 0, 1, 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