Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d60c45bf899bb1991340cd7fd8cbada9409fe19c910465a8166c13bd3d2dbd7a

Tx prefix hash: 8bd356de7eb9fa84c21aff48dfd92743f627359407767427d7aa9fbc82f03469
Tx public key: 7faa9618f910b1b86fd032cf52ecf1a3da1b2d9fdf069739e80170f5f08737c3
Timestamp: 1718084505 Timestamp [UCT]: 2024-06-11 05:41:45 Age [y:d:h:m:s]: 01:150:05:08:10
Block: 1041680 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 365914 RingCT/type: yes/0
Extra: 017faa9618f910b1b86fd032cf52ecf1a3da1b2d9fdf069739e80170f5f08737c30211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f4c9af794cd03675cffe92f58be7f76f54182d1ee8a5d65e12fceb9276b319ab 0.600000000000 1510413 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": 1041690, "vin": [ { "gen": { "height": 1041680 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f4c9af794cd03675cffe92f58be7f76f54182d1ee8a5d65e12fceb9276b319ab" } } ], "extra": [ 1, 127, 170, 150, 24, 249, 16, 177, 184, 111, 208, 50, 207, 82, 236, 241, 163, 218, 27, 45, 159, 223, 6, 151, 57, 232, 1, 112, 245, 240, 135, 55, 195, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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