Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f673af41c615901ebc69283c1152c2c1aa5eda82f14e0dee910e4ac816d86d5f

Tx prefix hash: 6007b16f42a0ceeb4fe3758027dbae41b783c672eed5751d65259d5d945a9347
Tx public key: c128bcf9dabe8902961c0bbec06190350336fb7628fb19d5836ecf9e8d78d306
Timestamp: 1673890061 Timestamp [UCT]: 2023-01-16 17:27:41 Age [y:d:h:m:s]: 02:107:07:07:01
Block: 676133 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 598379 RingCT/type: yes/0
Extra: 01c128bcf9dabe8902961c0bbec06190350336fb7628fb19d5836ecf9e8d78d3060211000000038b7b6602000000000000000000

1 output(s) for total of 3.529316797000 dcy

stealth address amount amount idx
00: 00add501c1d5bb72d45e1afb7535bd1efb03ffe9f8be3c50b5ac0eb0bef7d0cd 3.529316797000 1117842 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": 676143, "vin": [ { "gen": { "height": 676133 } } ], "vout": [ { "amount": 3529316797, "target": { "key": "00add501c1d5bb72d45e1afb7535bd1efb03ffe9f8be3c50b5ac0eb0bef7d0cd" } } ], "extra": [ 1, 193, 40, 188, 249, 218, 190, 137, 2, 150, 28, 11, 190, 192, 97, 144, 53, 3, 54, 251, 118, 40, 251, 25, 213, 131, 110, 207, 158, 141, 120, 211, 6, 2, 17, 0, 0, 0, 3, 139, 123, 102, 2, 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