Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e171700ffe3cf042ea5857d82896ff69c693652880462b88287ad8c6bd97de92

Tx prefix hash: c604c6ab5bd030ebd7d6b8b4e2fd264b7c5a33c1a2d3b6bcd1edea4ac5cea9e6
Tx public key: 0a63c6072e223c6af297d0d26b64cf3cb02d265be6f2802372d5eb0ed12fa963
Timestamp: 1650358866 Timestamp [UCT]: 2022-04-19 09:01:06 Age [y:d:h:m:s]: 03:262:16:41:32
Block: 483451 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 966126 RingCT/type: yes/0
Extra: 010a63c6072e223c6af297d0d26b64cf3cb02d265be6f2802372d5eb0ed12fa963021100000011cb8520c2000000000000000000

1 output(s) for total of 15.350636107000 dcy

stealth address amount amount idx
00: 2ad7ace3bf311b13e6b4fcbb910b709e72edff567acaaf1bf1aa707dda3151cf 15.350636107000 905134 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": 483461, "vin": [ { "gen": { "height": 483451 } } ], "vout": [ { "amount": 15350636107, "target": { "key": "2ad7ace3bf311b13e6b4fcbb910b709e72edff567acaaf1bf1aa707dda3151cf" } } ], "extra": [ 1, 10, 99, 198, 7, 46, 34, 60, 106, 242, 151, 208, 210, 107, 100, 207, 60, 176, 45, 38, 91, 230, 242, 128, 35, 114, 213, 235, 14, 209, 47, 169, 99, 2, 17, 0, 0, 0, 17, 203, 133, 32, 194, 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