Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 582aa88f1b2ef44af9e905167470c02568ff27de6370ffb7c341697bde95b95f

Tx prefix hash: 3bb7312c79e1422aa915a0a400161a70595a5ca60b813813c322a8799150b10d
Tx public key: 747c13003a969db1324ae28ecf649594a24d68f5892df1fb72f3eb21d3c1a2b8
Timestamp: 1729346265 Timestamp [UCT]: 2024-10-19 13:57:45 Age [y:d:h:m:s]: 00:036:07:46:40
Block: 1135039 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 25918 RingCT/type: yes/0
Extra: 01747c13003a969db1324ae28ecf649594a24d68f5892df1fb72f3eb21d3c1a2b8021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 54d411decd2c99bc868a23267365b70dc4d91ea41c55176d452992066b9dcb7a 0.600000000000 1618368 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": 1135049, "vin": [ { "gen": { "height": 1135039 } } ], "vout": [ { "amount": 600000000, "target": { "key": "54d411decd2c99bc868a23267365b70dc4d91ea41c55176d452992066b9dcb7a" } } ], "extra": [ 1, 116, 124, 19, 0, 58, 150, 157, 177, 50, 74, 226, 142, 207, 100, 149, 148, 162, 77, 104, 245, 137, 45, 241, 251, 114, 243, 235, 33, 211, 193, 162, 184, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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