Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a164f9841ea87cabcccad582e9712cd59d0024d2bd008b9de08c065be111475

Tx prefix hash: 82d482c135956094e2bb4497c1199831a693c091a252cafa2b075efbeaf7e51a
Tx public key: d003df2cac6e43cd1f5c6d3afe5d4034ef40245eaeadd5eb1ba5462ddd643da2
Timestamp: 1707003400 Timestamp [UCT]: 2024-02-03 23:36:40 Age [y:d:h:m:s]: 01:131:07:11:23
Block: 949793 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 354875 RingCT/type: yes/0
Extra: 01d003df2cac6e43cd1f5c6d3afe5d4034ef40245eaeadd5eb1ba5462ddd643da202110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 350e199d788825822fd9d1d5bbeeb2bf3d29607315f288b9444f5627ec2491b8 0.600000000000 1408325 of 15

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": 949803, "vin": [ { "gen": { "height": 949793 } } ], "vout": [ { "amount": 600000000, "target": { "key": "350e199d788825822fd9d1d5bbeeb2bf3d29607315f288b9444f5627ec2491b8" } } ], "extra": [ 1, 208, 3, 223, 44, 172, 110, 67, 205, 31, 92, 109, 58, 254, 93, 64, 52, 239, 64, 36, 94, 174, 173, 213, 235, 27, 165, 70, 45, 221, 100, 61, 162, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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