Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5985d5f2f02154730bf59efbb0e7c2faf720f17b6be06d863ac6164ae8acf0fb

Tx prefix hash: db87214a096355d7a4410f42a516f14e8f641355e27d4dd3dfdd6b95d15f00f1
Tx public key: 606d396925ba29efe1472fb9c41212aa3da2103fe36411cf03a4c4f137928f2d
Timestamp: 1658015753 Timestamp [UCT]: 2022-07-16 23:55:53 Age [y:d:h:m:s]: 02:335:04:12:46
Block: 545343 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 760650 RingCT/type: yes/0
Extra: 01606d396925ba29efe1472fb9c41212aa3da2103fe36411cf03a4c4f137928f2d02110000000175e3f0e9000000000000000000

1 output(s) for total of 9.573095633000 dcy

stealth address amount amount idx
00: b1b2e7f15ba6f203084e4214c04dcf876c164f828d9028fa03067c2c6094e8c1 9.573095633000 976222 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": 545353, "vin": [ { "gen": { "height": 545343 } } ], "vout": [ { "amount": 9573095633, "target": { "key": "b1b2e7f15ba6f203084e4214c04dcf876c164f828d9028fa03067c2c6094e8c1" } } ], "extra": [ 1, 96, 109, 57, 105, 37, 186, 41, 239, 225, 71, 47, 185, 196, 18, 18, 170, 61, 162, 16, 63, 227, 100, 17, 207, 3, 164, 196, 241, 55, 146, 143, 45, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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