Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e1c5f3bb82a3b0e31e0056171a02c3e5ab577d4d8b79666df2c160783488b879

Tx prefix hash: 9c549769c6e7d9444033416b422d4dc5609799dbc42de8df14af0ebb3398dced
Tx public key: afd3269e1b6c9f03f095919e94fd97fc23aecb9e9b910de7db30ed7442f802f7
Timestamp: 1748817165 Timestamp [UCT]: 2025-06-01 22:32:45 Age [y:d:h:m:s]: 00:162:00:49:51
Block: 1295915 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113488 RingCT/type: yes/0
Extra: 01afd3269e1b6c9f03f095919e94fd97fc23aecb9e9b910de7db30ed7442f802f702110000000543846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bbe883d0134f71a5392dc1105196e142f142c4b7e4444855414bc6e87401b61c 0.600000000000 1783422 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": 1295925, "vin": [ { "gen": { "height": 1295915 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bbe883d0134f71a5392dc1105196e142f142c4b7e4444855414bc6e87401b61c" } } ], "extra": [ 1, 175, 211, 38, 158, 27, 108, 159, 3, 240, 149, 145, 158, 148, 253, 151, 252, 35, 174, 203, 158, 155, 145, 13, 231, 219, 48, 237, 116, 66, 248, 2, 247, 2, 17, 0, 0, 0, 5, 67, 132, 109, 102, 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