Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f577d070501e5c3f5eeaeff759aea7db597f9ca939dd218e1c4fed934bba2a8

Tx prefix hash: 24e52b6cfe27a5f184600ab7ea2cdf51faa9c186ff1781792b8c5e6169ecbe3b
Tx public key: 7b66e5d4e0c4621a850864d19520cd870e41c7ed94e340f92b05d5f43452ef68
Timestamp: 1733264577 Timestamp [UCT]: 2024-12-03 22:22:57 Age [y:d:h:m:s]: 00:115:13:03:48
Block: 1167424 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82380 RingCT/type: yes/0
Extra: 017b66e5d4e0c4621a850864d19520cd870e41c7ed94e340f92b05d5f43452ef680211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c8666bf45ea258962c186aed7ea733cec5c4d35e17b485c64a96d3a713dad00b 0.600000000000 1653119 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": 1167434, "vin": [ { "gen": { "height": 1167424 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c8666bf45ea258962c186aed7ea733cec5c4d35e17b485c64a96d3a713dad00b" } } ], "extra": [ 1, 123, 102, 229, 212, 224, 196, 98, 26, 133, 8, 100, 209, 149, 32, 205, 135, 14, 65, 199, 237, 148, 227, 64, 249, 43, 5, 213, 244, 52, 82, 239, 104, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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