Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1126d2a7d92ede669ebc92a40df1a3eb0c6c7b42fa799a2dee54db47632eaca4

Tx prefix hash: 3caa71f1e7d455cbc4208bb1072fe0ca990c95bd7f7a8884033736a0765e1024
Tx public key: d1d092f1b94eaecb8a4243ba6467f890100442684da3ef808f1f298f189c22a1
Timestamp: 1577850873 Timestamp [UCT]: 2020-01-01 03:54:33 Age [y:d:h:m:s]: 04:322:18:17:28
Block: 36133 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1119840 RingCT/type: yes/0
Extra: 01d1d092f1b94eaecb8a4243ba6467f890100442684da3ef808f1f298f189c22a10211000000028a2ee0d9000000000000000000

1 output(s) for total of 465.883387665000 dcy

stealth address amount amount idx
00: 0b7ae85d3cf8466720fa77d64c3d3332e2b39a2ca2adaf9e63e0614296b87bf4 465.883387665000 61107 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": 36143, "vin": [ { "gen": { "height": 36133 } } ], "vout": [ { "amount": 465883387665, "target": { "key": "0b7ae85d3cf8466720fa77d64c3d3332e2b39a2ca2adaf9e63e0614296b87bf4" } } ], "extra": [ 1, 209, 208, 146, 241, 185, 78, 174, 203, 138, 66, 67, 186, 100, 103, 248, 144, 16, 4, 66, 104, 77, 163, 239, 128, 143, 31, 41, 143, 24, 156, 34, 161, 2, 17, 0, 0, 0, 2, 138, 46, 224, 217, 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