Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 586efd75b5fcc3567b19200ac260f2c29b0043a705394c719fcd8c376fd9de1f

Tx prefix hash: 87c7abaa80ba863dc2e751b5f68f2bd979df4ae46b71e615d20b9078734b799c
Tx public key: d7eb375965da4683466e4e4f7e807dc3edc6245d3eb60878d4258255c73f2dbc
Timestamp: 1673042744 Timestamp [UCT]: 2023-01-06 22:05:44 Age [y:d:h:m:s]: 02:330:16:44:07
Block: 669107 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 755793 RingCT/type: yes/0
Extra: 01d7eb375965da4683466e4e4f7e807dc3edc6245d3eb60878d4258255c73f2dbc02110000000552542ceb000000000000000000

1 output(s) for total of 3.723665903000 dcy

stealth address amount amount idx
00: f7024737f5dda3d381d1826ac0eb681648d4cac0dccfb3d61517a9ff5a0d374f 3.723665903000 1110408 of 0

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": 669117, "vin": [ { "gen": { "height": 669107 } } ], "vout": [ { "amount": 3723665903, "target": { "key": "f7024737f5dda3d381d1826ac0eb681648d4cac0dccfb3d61517a9ff5a0d374f" } } ], "extra": [ 1, 215, 235, 55, 89, 101, 218, 70, 131, 70, 110, 78, 79, 126, 128, 125, 195, 237, 198, 36, 93, 62, 182, 8, 120, 212, 37, 130, 85, 199, 63, 45, 188, 2, 17, 0, 0, 0, 5, 82, 84, 44, 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