Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 549e6607cc98ea89f13028d40c69d3f6c90ac4694fcd597339e66fcb851e5f02

Tx prefix hash: 789e8473fd566f198fdef98b0217ab61634cc14c2efa2481fc70dec757a7a2f1
Tx public key: 1fad16455c1d1320e473b51de7480b2acdf86c4b1fbddf121a6bc9efd8cf6853
Timestamp: 1665359195 Timestamp [UCT]: 2022-10-09 23:46:35 Age [y:d:h:m:s]: 03:022:01:14:04
Block: 605671 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 795924 RingCT/type: yes/0
Extra: 011fad16455c1d1320e473b51de7480b2acdf86c4b1fbddf121a6bc9efd8cf685302110000000452542ceb000000000000000000

1 output(s) for total of 6.041720114000 dcy

stealth address amount amount idx
00: 62a94b33942dfbf48be38e9fca8b8870e6f62b438487e85f7c12df444e0e63c0 6.041720114000 1042094 of 0

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": 605681, "vin": [ { "gen": { "height": 605671 } } ], "vout": [ { "amount": 6041720114, "target": { "key": "62a94b33942dfbf48be38e9fca8b8870e6f62b438487e85f7c12df444e0e63c0" } } ], "extra": [ 1, 31, 173, 22, 69, 92, 29, 19, 32, 228, 115, 181, 29, 231, 72, 11, 42, 205, 248, 108, 75, 31, 189, 223, 18, 26, 107, 201, 239, 216, 207, 104, 83, 2, 17, 0, 0, 0, 4, 82, 84, 44, 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