Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 59de96fc5dbaea4158a1b457ccdbdbcab8a6e87d285c1ddbf3244a7072acfaf1

Tx prefix hash: f91695dcbec46123614278142b0eb653c67a1f2c7040b580751142d0c409fbd1
Tx public key: ca7c00e47a4a3c412b30993ae1503c4c099ab6c853bd39b514baffa9a1151710
Timestamp: 1708529352 Timestamp [UCT]: 2024-02-21 15:29:12 Age [y:d:h:m:s]: 01:045:13:02:57
Block: 962455 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 293565 RingCT/type: yes/0
Extra: 01ca7c00e47a4a3c412b30993ae1503c4c099ab6c853bd39b514baffa9a115171002110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b75161a3be3f2daa083dbb31dd06d7b7a2db337634522f99cf6e31d24b77d776 0.600000000000 1422092 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": 962465, "vin": [ { "gen": { "height": 962455 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b75161a3be3f2daa083dbb31dd06d7b7a2db337634522f99cf6e31d24b77d776" } } ], "extra": [ 1, 202, 124, 0, 228, 122, 74, 60, 65, 43, 48, 153, 58, 225, 80, 60, 76, 9, 154, 182, 200, 83, 189, 57, 181, 20, 186, 255, 169, 161, 21, 23, 16, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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