Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 82f5739004e5cefb892dd607e31e884b942564b91869832bc525ae759d6817aa

Tx prefix hash: d598463be8927110963327b7e20945a29a94623f7be1c19ce2abc8a8e5ca5da2
Tx public key: a2861e1f9ef9b36be070429acff9abc4423104da1c945a477da18ad61912967a
Timestamp: 1724049649 Timestamp [UCT]: 2024-08-19 06:40:49 Age [y:d:h:m:s]: 00:223:01:45:23
Block: 1091133 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159287 RingCT/type: yes/0
Extra: 01a2861e1f9ef9b36be070429acff9abc4423104da1c945a477da18ad61912967a021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b17c464a88c9664d3f66938222b6aa7ac0cfa6f1f297719d9d49994cb4e8e9d5 0.600000000000 1565762 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": 1091143, "vin": [ { "gen": { "height": 1091133 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b17c464a88c9664d3f66938222b6aa7ac0cfa6f1f297719d9d49994cb4e8e9d5" } } ], "extra": [ 1, 162, 134, 30, 31, 158, 249, 179, 107, 224, 112, 66, 154, 207, 249, 171, 196, 66, 49, 4, 218, 28, 148, 90, 71, 125, 161, 138, 214, 25, 18, 150, 122, 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