Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 95de74273f3ac3ead44cec5f004a188ab49cb1e7d22007e88c5ed55cac3b91a0

Tx prefix hash: 757672c76e69af262857dd0da97d10c7aeffe7ac1e681eddf4558ce15145a70b
Tx public key: b82e0aae425aef8cbd5fddd7dd91bbe8d73df44e1cb75f99f6ed697b55af1363
Timestamp: 1750406467 Timestamp [UCT]: 2025-06-20 08:01:07 Age [y:d:h:m:s]: 00:142:14:04:08
Block: 1308917 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99740 RingCT/type: yes/0
Extra: 01b82e0aae425aef8cbd5fddd7dd91bbe8d73df44e1cb75f99f6ed697b55af136302110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0bd4a383a99d0f6adbf77dedd8be4da90fee754f0e0de251ff666c06c65d401 0.600000000000 1796532 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": 1308927, "vin": [ { "gen": { "height": 1308917 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0bd4a383a99d0f6adbf77dedd8be4da90fee754f0e0de251ff666c06c65d401" } } ], "extra": [ 1, 184, 46, 10, 174, 66, 90, 239, 140, 189, 95, 221, 215, 221, 145, 187, 232, 215, 61, 244, 78, 28, 183, 95, 153, 246, 237, 105, 123, 85, 175, 19, 99, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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