Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8463b5adb2fc66cde0590b960ca95d9fd9f7ebb19ea780a647a1262999cbebfa

Tx prefix hash: 7f1de1e6295073019cd2658d78961228e583ef42617881fef6e1c431da85945d
Tx public key: 72796879bd4e13e824be3c6fd0ec213c67a03bde2d76a244af7a38084b1828be
Timestamp: 1719488651 Timestamp [UCT]: 2024-06-27 11:44:11 Age [y:d:h:m:s]: 01:139:04:56:14
Block: 1053313 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 358039 RingCT/type: yes/0
Extra: 0172796879bd4e13e824be3c6fd0ec213c67a03bde2d76a244af7a38084b1828be02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 55815f9b5305e549aa4fc25177e5c3e88b407c1443fd6feec4cfbf51345d2bbc 0.600000000000 1523660 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": 1053323, "vin": [ { "gen": { "height": 1053313 } } ], "vout": [ { "amount": 600000000, "target": { "key": "55815f9b5305e549aa4fc25177e5c3e88b407c1443fd6feec4cfbf51345d2bbc" } } ], "extra": [ 1, 114, 121, 104, 121, 189, 78, 19, 232, 36, 190, 60, 111, 208, 236, 33, 60, 103, 160, 59, 222, 45, 118, 162, 68, 175, 122, 56, 8, 75, 24, 40, 190, 2, 17, 0, 0, 0, 3, 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