Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8819e11df89a8534b0d838d00d7fff7e18db60bef009ba22e7a3d0238fae3d86

Tx prefix hash: 90da5f349a5866533f2cc97893f3bfbefceeb3c1152c27a3ab240ae5f4cc50cb
Tx public key: 2f65e595a950db830db70fd419f941973e78b8ff5a37edc9aa51dc5f97898346
Timestamp: 1764945868 Timestamp [UCT]: 2025-12-05 14:44:28 Age [y:d:h:m:s]: 00:028:16:59:23
Block: 1427042 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 20569 RingCT/type: yes/0
Extra: 012f65e595a950db830db70fd419f941973e78b8ff5a37edc9aa51dc5f97898346021100000002fb8fd089000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9dca02f97b25e40204d18636b84fc9762979b44624cfcde59fc30d4999a0aeaf 0.600000000000 1915741 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": 1427052, "vin": [ { "gen": { "height": 1427042 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9dca02f97b25e40204d18636b84fc9762979b44624cfcde59fc30d4999a0aeaf" } } ], "extra": [ 1, 47, 101, 229, 149, 169, 80, 219, 131, 13, 183, 15, 212, 25, 249, 65, 151, 62, 120, 184, 255, 90, 55, 237, 201, 170, 81, 220, 95, 151, 137, 131, 70, 2, 17, 0, 0, 0, 2, 251, 143, 208, 137, 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