Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 655f420da9089fbab4973e4124912ff1205166e46c0413f04e84f7df65832334

Tx prefix hash: 0ea8c9edf254ae470c3e9da27c6b57af5355b0153976765dd3e8ce3e5f5be9b3
Tx public key: b91f9c4334e8190621722f5e4d5780d5d40c0378218c76df4d0aeda78bac6243
Timestamp: 1580707609 Timestamp [UCT]: 2020-02-03 05:26:49 Age [y:d:h:m:s]: 04:288:10:16:53
Block: 57791 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1097252 RingCT/type: yes/0
Extra: 01b91f9c4334e8190621722f5e4d5780d5d40c0378218c76df4d0aeda78bac624302110000002a4943cd9f000000000000000000

1 output(s) for total of 394.945725217000 dcy

stealth address amount amount idx
00: d80a4d3b4924926b462a0493a6c72d4f6a4bda8b6fd535d10bdd8df305c33eca 394.945725217000 106809 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": 57801, "vin": [ { "gen": { "height": 57791 } } ], "vout": [ { "amount": 394945725217, "target": { "key": "d80a4d3b4924926b462a0493a6c72d4f6a4bda8b6fd535d10bdd8df305c33eca" } } ], "extra": [ 1, 185, 31, 156, 67, 52, 232, 25, 6, 33, 114, 47, 94, 77, 87, 128, 213, 212, 12, 3, 120, 33, 140, 118, 223, 77, 10, 237, 167, 139, 172, 98, 67, 2, 17, 0, 0, 0, 42, 73, 67, 205, 159, 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