Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d30db2833018a573f857f665c88b481e4b2841a8ec93600d9a8965cd40803d6a

Tx prefix hash: 99d16f055499bd0752095436b5a75190d1a514e4ba391ca9f1705915245eca52
Tx public key: 0491365033aeaa4d25d2c4f758700fb8b78dee9e02191941eba028a239c4ae1f
Timestamp: 1713999777 Timestamp [UCT]: 2024-04-24 23:02:57 Age [y:d:h:m:s]: 01:222:02:17:19
Block: 1007809 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 417413 RingCT/type: yes/0
Extra: 010491365033aeaa4d25d2c4f758700fb8b78dee9e02191941eba028a239c4ae1f02110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8bcf7632642a04603aee204cd2476d100425c89a4a92aae00bb9ba8b8160a6b3 0.600000000000 1469267 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": 1007819, "vin": [ { "gen": { "height": 1007809 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8bcf7632642a04603aee204cd2476d100425c89a4a92aae00bb9ba8b8160a6b3" } } ], "extra": [ 1, 4, 145, 54, 80, 51, 174, 170, 77, 37, 210, 196, 247, 88, 112, 15, 184, 183, 141, 238, 158, 2, 25, 25, 65, 235, 160, 40, 162, 57, 196, 174, 31, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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