Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3cdc30504048df0307f1bc4b468959b976f003370e596852588072a3e3c4b3cf

Tx prefix hash: c3007d4ccd89f042fd53bc37604dc73ac2e0547cf21013b6443d029cf8f02c0b
Tx public key: fe916b7146a89f2d7ecd04391c60fde781f185ffe44d38130a033f888df0bc1e
Timestamp: 1727468452 Timestamp [UCT]: 2024-09-27 20:20:52 Age [y:d:h:m:s]: 00:117:07:32:39
Block: 1119474 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83839 RingCT/type: yes/0
Extra: 01fe916b7146a89f2d7ecd04391c60fde781f185ffe44d38130a033f888df0bc1e02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a540fbd14c41763f6c3f2028337a3a85275b0e457b9c9b86a2108b578f5ab0af 0.600000000000 1601045 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": 1119484, "vin": [ { "gen": { "height": 1119474 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a540fbd14c41763f6c3f2028337a3a85275b0e457b9c9b86a2108b578f5ab0af" } } ], "extra": [ 1, 254, 145, 107, 113, 70, 168, 159, 45, 126, 205, 4, 57, 28, 96, 253, 231, 129, 241, 133, 255, 228, 77, 56, 19, 10, 3, 63, 136, 141, 240, 188, 30, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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