Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4753cc61f8b3f2aa553a48ce72a551f898b21fca8d20cadd93bd55eb86ac7b7e

Tx prefix hash: 8e1d5f243a7aa651c79dedd0f5d998f0898ebc8bb6b79f630566b5827816cb54
Tx public key: cbb5cac2a0ddcea7c37c925e7cbcb549c142f0b5040511dce9120b6dd8894bf5
Timestamp: 1736139549 Timestamp [UCT]: 2025-01-06 04:59:09 Age [y:d:h:m:s]: 00:084:02:23:20
Block: 1191238 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 59867 RingCT/type: yes/0
Extra: 01cbb5cac2a0ddcea7c37c925e7cbcb549c142f0b5040511dce9120b6dd8894bf50211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1514d6ec47426a18ff197eb3eb774693bb2a20dc8b130a40653a8041d90663b2 0.600000000000 1677761 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": 1191248, "vin": [ { "gen": { "height": 1191238 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1514d6ec47426a18ff197eb3eb774693bb2a20dc8b130a40653a8041d90663b2" } } ], "extra": [ 1, 203, 181, 202, 194, 160, 221, 206, 167, 195, 124, 146, 94, 124, 188, 181, 73, 193, 66, 240, 181, 4, 5, 17, 220, 233, 18, 11, 109, 216, 137, 75, 245, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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