Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0864b6260aa10b1f89773ab7734e310e963c3bbe6eda7aa31dc749229e4188c

Tx prefix hash: b71728bf94bb45dd36fbe224682f4d3651f66818c795942a33948dfc3051e32d
Tx public key: 498946a6460335cb8a6019e29757a2f06bfd54094fd5a914b53f87e421c67a76
Timestamp: 1755235011 Timestamp [UCT]: 2025-08-15 05:16:51 Age [y:d:h:m:s]: 00:091:20:18:03
Block: 1346998 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 65341 RingCT/type: yes/0
Extra: 01498946a6460335cb8a6019e29757a2f06bfd54094fd5a914b53f87e421c67a76021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e1b0b3e2aa3be4d511ddfbcb7618742eadfc5094cda33ba1ab7fd79bf082f45e 0.600000000000 1834911 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": 1347008, "vin": [ { "gen": { "height": 1346998 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e1b0b3e2aa3be4d511ddfbcb7618742eadfc5094cda33ba1ab7fd79bf082f45e" } } ], "extra": [ 1, 73, 137, 70, 166, 70, 3, 53, 203, 138, 96, 25, 226, 151, 87, 162, 240, 107, 253, 84, 9, 79, 213, 169, 20, 181, 63, 135, 228, 33, 198, 122, 118, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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