Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd51807f32923729f85db68b59397b3e3710d1d98b03dff4318ead283b13b389

Tx prefix hash: 7b4a386011146ea1c7809e62da89a40eb5f12a89227e996a9b8685cf021548b8
Tx public key: 3847818d5f4bbf39489fbcd1f4e283f09837c882bfb16c9c32268508542be035
Timestamp: 1712565489 Timestamp [UCT]: 2024-04-08 08:38:09 Age [y:d:h:m:s]: 01:067:23:26:31
Block: 995891 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309519 RingCT/type: yes/0
Extra: 013847818d5f4bbf39489fbcd1f4e283f09837c882bfb16c9c32268508542be03502110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 308b7aaa2729c7f86cf16b174a407a4ea0e9a873b31a6dc34faab91a9a91db8b 0.600000000000 1456305 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": 995901, "vin": [ { "gen": { "height": 995891 } } ], "vout": [ { "amount": 600000000, "target": { "key": "308b7aaa2729c7f86cf16b174a407a4ea0e9a873b31a6dc34faab91a9a91db8b" } } ], "extra": [ 1, 56, 71, 129, 141, 95, 75, 191, 57, 72, 159, 188, 209, 244, 226, 131, 240, 152, 55, 200, 130, 191, 177, 108, 156, 50, 38, 133, 8, 84, 43, 224, 53, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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