Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c488bd40d83eaefd5d66f5e2c2c19eff74ddadcd9ceba12a603e12f85c4176bc

Tx prefix hash: 3461ba08418ac1ed4b13870d2ef3244de5c9c2fbcdcbe3b514fe241358c7c1a3
Tx public key: 9a6427952e3334895a495f497a6c00a3ba5721a61b5c22b0e20120598e55163d
Timestamp: 1727699400 Timestamp [UCT]: 2024-09-30 12:30:00 Age [y:d:h:m:s]: 00:235:20:41:09
Block: 1121389 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 168417 RingCT/type: yes/0
Extra: 019a6427952e3334895a495f497a6c00a3ba5721a61b5c22b0e20120598e55163d021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: dffa7aae42eaebd6618a484376110fa53751d4f6bb10d0d9f3f1f421ac4b303a 0.600000000000 1603644 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": 1121399, "vin": [ { "gen": { "height": 1121389 } } ], "vout": [ { "amount": 600000000, "target": { "key": "dffa7aae42eaebd6618a484376110fa53751d4f6bb10d0d9f3f1f421ac4b303a" } } ], "extra": [ 1, 154, 100, 39, 149, 46, 51, 52, 137, 90, 73, 95, 73, 122, 108, 0, 163, 186, 87, 33, 166, 27, 92, 34, 176, 226, 1, 32, 89, 142, 85, 22, 61, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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