Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 315e3d260f44069211b331293e89767f4afa6f3e581ed516b6e602c1dea81e27

Tx prefix hash: 444b17d284d9788ab621f5113c5e9ce29c01d2f09b7ce490e50c5997807b5463
Tx public key: 898e7fb0bf0f1b624bf7ccea5fc525e390d1f3f2c314c62e9dedebc0a6ecc443
Timestamp: 1730812612 Timestamp [UCT]: 2024-11-05 13:16:52 Age [y:d:h:m:s]: 00:140:16:07:24
Block: 1147104 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100362 RingCT/type: yes/0
Extra: 01898e7fb0bf0f1b624bf7ccea5fc525e390d1f3f2c314c62e9dedebc0a6ecc443021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2209356ba4b95ace7edd4a6bf44964de51b0c829bebe06f375de9e6b8ef871b0 0.600000000000 1631797 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": 1147114, "vin": [ { "gen": { "height": 1147104 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2209356ba4b95ace7edd4a6bf44964de51b0c829bebe06f375de9e6b8ef871b0" } } ], "extra": [ 1, 137, 142, 127, 176, 191, 15, 27, 98, 75, 247, 204, 234, 95, 197, 37, 227, 144, 209, 243, 242, 195, 20, 198, 46, 157, 237, 235, 192, 166, 236, 196, 67, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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