Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b14c8519c46808193ef963f539ba30413d90d82e7b02564277ad2fa7a9d7d71

Tx prefix hash: c0c588b1577415ebd2bd0b5f3ef6d01fba529c756f6ce455e6462f62f36f2e8d
Tx public key: 39741b5617a2c70397f7d3d3417e973a86fca45a27b037fce659e89ecd970ece
Timestamp: 1722610519 Timestamp [UCT]: 2024-08-02 14:55:19 Age [y:d:h:m:s]: 00:241:23:20:53
Block: 1079200 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172823 RingCT/type: yes/0
Extra: 0139741b5617a2c70397f7d3d3417e973a86fca45a27b037fce659e89ecd970ece021100000004ef5a8513000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d5f4baf70e1c7415e59b9a17a385f0dc1e803de1436e9395f8db0ad699075b05 0.600000000000 1552047 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": 1079210, "vin": [ { "gen": { "height": 1079200 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d5f4baf70e1c7415e59b9a17a385f0dc1e803de1436e9395f8db0ad699075b05" } } ], "extra": [ 1, 57, 116, 27, 86, 23, 162, 199, 3, 151, 247, 211, 211, 65, 126, 151, 58, 134, 252, 164, 90, 39, 176, 55, 252, 230, 89, 232, 158, 205, 151, 14, 206, 2, 17, 0, 0, 0, 4, 239, 90, 133, 19, 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