Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 74596eeaf7329bf44d3bacf7d5050ba100398fbecf733b68a323ef3cf6639c2f

Tx prefix hash: 549c1e93099574824296f82bb74648499fbc1a2f97716a1e28a3eb991391a6fe
Tx public key: facd1bc0d60b71b7cce4e2fc3e67e87d3bd7793f5edae39a301ef580a24caa01
Timestamp: 1634762807 Timestamp [UCT]: 2021-10-20 20:46:47 Age [y:d:h:m:s]: 03:188:22:44:58
Block: 357004 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 913075 RingCT/type: yes/0
Extra: 01facd1bc0d60b71b7cce4e2fc3e67e87d3bd7793f5edae39a301ef580a24caa010211000000168d0de867000000000000000000

1 output(s) for total of 40.281488370000 dcy

stealth address amount amount idx
00: 16faac5e4f8950a8b690a9af8303a0b690871696f2e8bc577078ae839f07a710 40.281488370000 728150 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": 357014, "vin": [ { "gen": { "height": 357004 } } ], "vout": [ { "amount": 40281488370, "target": { "key": "16faac5e4f8950a8b690a9af8303a0b690871696f2e8bc577078ae839f07a710" } } ], "extra": [ 1, 250, 205, 27, 192, 214, 11, 113, 183, 204, 228, 226, 252, 62, 103, 232, 125, 59, 215, 121, 63, 94, 218, 227, 154, 48, 30, 245, 128, 162, 76, 170, 1, 2, 17, 0, 0, 0, 22, 141, 13, 232, 103, 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