Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 319e77dd7bd95e654927696ae42c4f98119a816c2dbe204123e76f87f998a58c

Tx prefix hash: aaeef5200ed8c8b01c524d6c739c0c2e09c36d82ab15e27df03e6b039eace622
Tx public key: 163654b8191a96323191bed934b1597240f1f4f231a15d3aa23c5d10329dc3c0
Timestamp: 1712651532 Timestamp [UCT]: 2024-04-09 08:32:12 Age [y:d:h:m:s]: 01:043:00:57:12
Block: 996614 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 291761 RingCT/type: yes/0
Extra: 01163654b8191a96323191bed934b1597240f1f4f231a15d3aa23c5d10329dc3c00211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d3145dc00ae9329df02981ae42389778116e09e66e7c346e41116ff7497975fe 0.600000000000 1457036 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": 996624, "vin": [ { "gen": { "height": 996614 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d3145dc00ae9329df02981ae42389778116e09e66e7c346e41116ff7497975fe" } } ], "extra": [ 1, 22, 54, 84, 184, 25, 26, 150, 50, 49, 145, 190, 217, 52, 177, 89, 114, 64, 241, 244, 242, 49, 161, 93, 58, 162, 60, 93, 16, 50, 157, 195, 192, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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