Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e1fb5c09432037e0d50e2326e574402c8ef1f07882baa16dedf95a35c89c550

Tx prefix hash: 30168a7f4c19330954b02109e0e60e504d93973e026a954126600a7d85cf74f6
Tx public key: 05dc861bf013db726da4d7cc12edfc631441972d5ce9c6f044d460f0f08ca6f8
Timestamp: 1762204734 Timestamp [UCT]: 2025-11-03 21:18:54 Age [y:d:h:m:s]: 00:061:07:28:11
Block: 1404325 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 43914 RingCT/type: yes/0
Extra: 0105dc861bf013db726da4d7cc12edfc631441972d5ce9c6f044d460f0f08ca6f8021100000003df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6d99a4e684c3c09e1037fe0b8b510f045e3a241bc1395a34db39a015760b1bdf 0.600000000000 1892682 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": 1404335, "vin": [ { "gen": { "height": 1404325 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6d99a4e684c3c09e1037fe0b8b510f045e3a241bc1395a34db39a015760b1bdf" } } ], "extra": [ 1, 5, 220, 134, 27, 240, 19, 219, 114, 109, 164, 215, 204, 18, 237, 252, 99, 20, 65, 151, 45, 92, 233, 198, 240, 68, 212, 96, 240, 240, 140, 166, 248, 2, 17, 0, 0, 0, 3, 223, 90, 36, 122, 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