Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b9a65e98b9ca363a9252dc24e86615df55b8728fd5af78068ee9485c7a2af788

Tx prefix hash: 2a101b9e1fdb4f2845cc3c2d3104d5e25c9f85433dc1fc40f2cb4835b02d4b1a
Tx public key: 2778cb6df854f279452a66c1f08aa341d5e751e08bd091ef959cf6e9a56e54ba
Timestamp: 1747362455 Timestamp [UCT]: 2025-05-16 02:27:35 Age [y:d:h:m:s]: 00:145:15:48:32
Block: 1283863 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101753 RingCT/type: yes/0
Extra: 012778cb6df854f279452a66c1f08aa341d5e751e08bd091ef959cf6e9a56e54ba021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bbd08efe8957cc25175ae10cde7896ea823ede7e8b9476f8d2fd390d34d7fbfd 0.600000000000 1771284 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": 1283873, "vin": [ { "gen": { "height": 1283863 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bbd08efe8957cc25175ae10cde7896ea823ede7e8b9476f8d2fd390d34d7fbfd" } } ], "extra": [ 1, 39, 120, 203, 109, 248, 84, 242, 121, 69, 42, 102, 193, 240, 138, 163, 65, 213, 231, 81, 224, 139, 208, 145, 239, 149, 156, 246, 233, 165, 110, 84, 186, 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