Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f126dbfcc05843ecf4980f3356af71044fdfde6d28dcfbbfc4340023aee11dcd

Tx prefix hash: 476d896c98ec5ba6a58baab59e1ec21e706f5567186f36eb3cc77f68a3c20f8b
Tx public key: 80a73c2996913a0c7ed897406a928ea4c6c21f7e9783498af2ed639bec806590
Timestamp: 1612174365 Timestamp [UCT]: 2021-02-01 10:12:45 Age [y:d:h:m:s]: 03:288:01:22:59
Block: 189675 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 964542 RingCT/type: yes/0
Extra: 0180a73c2996913a0c7ed897406a928ea4c6c21f7e9783498af2ed639bec8065900211000001c54ea414e5000000000000000000

1 output(s) for total of 144.389676599000 dcy

stealth address amount amount idx
00: 0e547adfa7cc3150948cb0c8fb5b95ef3efe2287633bb3ba383a0c1d1c574341 144.389676599000 379229 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": 189685, "vin": [ { "gen": { "height": 189675 } } ], "vout": [ { "amount": 144389676599, "target": { "key": "0e547adfa7cc3150948cb0c8fb5b95ef3efe2287633bb3ba383a0c1d1c574341" } } ], "extra": [ 1, 128, 167, 60, 41, 150, 145, 58, 12, 126, 216, 151, 64, 106, 146, 142, 164, 198, 194, 31, 126, 151, 131, 73, 138, 242, 237, 99, 155, 236, 128, 101, 144, 2, 17, 0, 0, 1, 197, 78, 164, 20, 229, 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