Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6323b7bb5ebfa4ac5787dd0debdb12c60a778d7ace61f82712cf16c2025f1dd

Tx prefix hash: 271a4ffb313a1e0e60b64580ff26c9b17ae47687e9da9e9f5e589c40e6f0e709
Tx public key: ddfa46ce73d5e0b075f4d17de84c2678865565eb761d9f82484ebbe9ea511934
Timestamp: 1582294393 Timestamp [UCT]: 2020-02-21 14:13:13 Age [y:d:h:m:s]: 05:231:13:44:44
Block: 69606 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1316305 RingCT/type: yes/0
Extra: 01ddfa46ce73d5e0b075f4d17de84c2678865565eb761d9f82484ebbe9ea511934021100000001724f989b000000000000000000

1 output(s) for total of 360.883670640000 dcy

stealth address amount amount idx
00: 04cbb9c182eca9c163e7c4e060ade7eebbb9f2c7b5d92c5ccab245396ad75423 360.883670640000 128369 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": 69616, "vin": [ { "gen": { "height": 69606 } } ], "vout": [ { "amount": 360883670640, "target": { "key": "04cbb9c182eca9c163e7c4e060ade7eebbb9f2c7b5d92c5ccab245396ad75423" } } ], "extra": [ 1, 221, 250, 70, 206, 115, 213, 224, 176, 117, 244, 209, 125, 232, 76, 38, 120, 134, 85, 101, 235, 118, 29, 159, 130, 72, 78, 187, 233, 234, 81, 25, 52, 2, 17, 0, 0, 0, 1, 114, 79, 152, 155, 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