Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf4591803f70ba06a4568390aa5e40781d51db88cd83978f92dc2d75c4b8afe1

Tx prefix hash: 62c83a639a785b4f795ed6569245ade2cc69ceffc01e244215896dd316b37d48
Tx public key: 00251fd851593d0f178ae913a8aa1b3f4c4f8a3612bcee6c983f2329d2761ef3
Timestamp: 1762039110 Timestamp [UCT]: 2025-11-01 23:18:30 Age [y:d:h:m:s]: 00:010:09:53:44
Block: 1402965 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7444 RingCT/type: yes/0
Extra: 0100251fd851593d0f178ae913a8aa1b3f4c4f8a3612bcee6c983f2329d2761ef302110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a67be480c8da4c957077ed2b9750e74ada683b837e5177346acc16459d66a96 0.600000000000 1891290 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": 1402975, "vin": [ { "gen": { "height": 1402965 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a67be480c8da4c957077ed2b9750e74ada683b837e5177346acc16459d66a96" } } ], "extra": [ 1, 0, 37, 31, 216, 81, 89, 61, 15, 23, 138, 233, 19, 168, 170, 27, 63, 76, 79, 138, 54, 18, 188, 238, 108, 152, 63, 35, 41, 210, 118, 30, 243, 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