Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e514de5ca78a5bc83298f2692587fb4b56db795dea94bc72e7ba5ef3f62df34d

Tx prefix hash: bd90f5948fd6fe3f71cf11ebbdf7703a299aa0d2c1c6e712d58abf0172445511
Tx public key: 99bce30412cd3581d7a403d9bb1f955d5ddc1da1c0b1a2ba74957a417f836400
Timestamp: 1737604701 Timestamp [UCT]: 2025-01-23 03:58:21 Age [y:d:h:m:s]: 00:148:19:49:03
Block: 1203313 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106059 RingCT/type: yes/0
Extra: 0199bce30412cd3581d7a403d9bb1f955d5ddc1da1c0b1a2ba74957a417f836400021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8bf54df2333548da21b787cfdb12b7944df6baf93a124274124609299f626dc5 0.600000000000 1689988 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": 1203323, "vin": [ { "gen": { "height": 1203313 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8bf54df2333548da21b787cfdb12b7944df6baf93a124274124609299f626dc5" } } ], "extra": [ 1, 153, 188, 227, 4, 18, 205, 53, 129, 215, 164, 3, 217, 187, 31, 149, 93, 93, 220, 29, 161, 192, 177, 162, 186, 116, 149, 122, 65, 127, 131, 100, 0, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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