Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d9b81b9420d8a126ba0f26c3de02cd3281299739c058e36eae667379e90c79f8

Tx prefix hash: be8039d7649878e3488fb00d146c45879f7988e62631c43911f824ec0dbb2e1a
Tx public key: 4630ae71dbf174e1a39903fafdb30f905eb8d38fabf4048d1b3f09772c789f37
Timestamp: 1745744635 Timestamp [UCT]: 2025-04-27 09:03:55 Age [y:d:h:m:s]: 00:015:09:27:20
Block: 1270480 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 11001 RingCT/type: yes/0
Extra: 014630ae71dbf174e1a39903fafdb30f905eb8d38fabf4048d1b3f09772c789f370211000000039f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb9a7577c9460b7d8fad8054b0e6db5b267dbbe47327b1335511cddc75827c6c 0.600000000000 1757723 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": 1270490, "vin": [ { "gen": { "height": 1270480 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb9a7577c9460b7d8fad8054b0e6db5b267dbbe47327b1335511cddc75827c6c" } } ], "extra": [ 1, 70, 48, 174, 113, 219, 241, 116, 225, 163, 153, 3, 250, 253, 179, 15, 144, 94, 184, 211, 143, 171, 244, 4, 141, 27, 63, 9, 119, 44, 120, 159, 55, 2, 17, 0, 0, 0, 3, 159, 159, 230, 140, 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