Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9da5e380fd98acaec67b97b3551575a14bb29c8acaca2379e90b90b58b196637

Tx prefix hash: 4783ecab02f917c40851fd6bb8c58bbde2710c67a81f745a9e19547036216897
Tx public key: 9fb4368bbdf99c49b5557d993d51a07cd62bf0f0c84dab0daaea6fce083a6c1a
Timestamp: 1721750593 Timestamp [UCT]: 2024-07-23 16:03:13 Age [y:d:h:m:s]: 00:304:05:29:44
Block: 1072056 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 217401 RingCT/type: yes/0
Extra: 019fb4368bbdf99c49b5557d993d51a07cd62bf0f0c84dab0daaea6fce083a6c1a021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a9f887c0ebb4cf55dc8ac15dc66b47c55eaa6894927f087664e1afcc895a09ed 0.600000000000 1544491 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": 1072066, "vin": [ { "gen": { "height": 1072056 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a9f887c0ebb4cf55dc8ac15dc66b47c55eaa6894927f087664e1afcc895a09ed" } } ], "extra": [ 1, 159, 180, 54, 139, 189, 249, 156, 73, 181, 85, 125, 153, 61, 81, 160, 124, 214, 43, 240, 240, 200, 77, 171, 13, 170, 234, 111, 206, 8, 58, 108, 26, 2, 17, 0, 0, 0, 2, 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