Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf68fba955bc1865f7ae0e4d048c59501e2ca9884582ce04587236f51f652ca2

Tx prefix hash: e67125c6d2dacf99a51ff9f666fa5d5905101e0e5a39b4a642e1d9abb52e3b2f
Tx public key: 319e6ebca7ac317e828c57978b8da8710872710ddd4ee31c336d33987c0ce581
Timestamp: 1750963426 Timestamp [UCT]: 2025-06-26 18:43:46 Age [y:d:h:m:s]: 00:147:22:35:01
Block: 1313348 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103742 RingCT/type: yes/0
Extra: 01319e6ebca7ac317e828c57978b8da8710872710ddd4ee31c336d33987c0ce581021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d87d848de208b91c7927df7dc823d3e8c97843873b2d76b38cadc0830f9df13 0.600000000000 1800987 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": 1313358, "vin": [ { "gen": { "height": 1313348 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d87d848de208b91c7927df7dc823d3e8c97843873b2d76b38cadc0830f9df13" } } ], "extra": [ 1, 49, 158, 110, 188, 167, 172, 49, 126, 130, 140, 87, 151, 139, 141, 168, 113, 8, 114, 113, 13, 221, 78, 227, 28, 51, 109, 51, 152, 124, 12, 229, 129, 2, 17, 0, 0, 0, 2, 228, 220, 144, 9, 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