Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2de6b10cf8aaf0d98591752dc12cd0e120eeb8a5de4897b9035f6018b3d1c76d

Tx prefix hash: a00cd06c4cc3bc1bb01db6e7b173cfed22f6c5ccd15639dc4b08b12860ac7587
Tx public key: 0968d65d7c8f1dbb036a4d8e0145ae4602fdbe5ad0a4bb4407088dfe4165c647
Timestamp: 1578661656 Timestamp [UCT]: 2020-01-10 13:07:36 Age [y:d:h:m:s]: 05:005:18:51:18
Block: 42703 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1154329 RingCT/type: yes/0
Extra: 010968d65d7c8f1dbb036a4d8e0145ae4602fdbe5ad0a4bb4407088dfe4165c647021100000017b221b3d1000000000000000000

1 output(s) for total of 443.106456129000 dcy

stealth address amount amount idx
00: ee9ac69cf8c6722be737a4c5ec90d1e194801b92b7db0d3c44b8f8caf5b53cf2 443.106456129000 77021 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": 42713, "vin": [ { "gen": { "height": 42703 } } ], "vout": [ { "amount": 443106456129, "target": { "key": "ee9ac69cf8c6722be737a4c5ec90d1e194801b92b7db0d3c44b8f8caf5b53cf2" } } ], "extra": [ 1, 9, 104, 214, 93, 124, 143, 29, 187, 3, 106, 77, 142, 1, 69, 174, 70, 2, 253, 190, 90, 208, 164, 187, 68, 7, 8, 141, 254, 65, 101, 198, 71, 2, 17, 0, 0, 0, 23, 178, 33, 179, 209, 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