Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3813adb352aa57823cd79dbf63f38459ce8cc9f9f14292613dd7a4d97a0dfb2d

Tx prefix hash: ea602de06eed5d808ec589d5ce0e52ec80a8dd9e444442e2217048e1bc9b3754
Tx public key: 0ffcc7789f8067df0ba96f6f9bd567d43cf80cddeef81ac9c4b1edbe66a94e08
Timestamp: 1705567338 Timestamp [UCT]: 2024-01-18 08:42:18 Age [y:d:h:m:s]: 01:083:20:35:47
Block: 937887 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321031 RingCT/type: yes/0
Extra: 010ffcc7789f8067df0ba96f6f9bd567d43cf80cddeef81ac9c4b1edbe66a94e080211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a99e500ed79c1fc581d2c8797f75ad7f7a0d702b12163c5b18f11fa6641f035d 0.600000000000 1395951 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": 937897, "vin": [ { "gen": { "height": 937887 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a99e500ed79c1fc581d2c8797f75ad7f7a0d702b12163c5b18f11fa6641f035d" } } ], "extra": [ 1, 15, 252, 199, 120, 159, 128, 103, 223, 11, 169, 111, 111, 155, 213, 103, 212, 60, 248, 12, 221, 238, 248, 26, 201, 196, 177, 237, 190, 102, 169, 78, 8, 2, 17, 0, 0, 0, 1, 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