Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a43fccc5f256462952353faa8bde7c8d5a2b5a6f67cf0404fbde2785a39a2506

Tx prefix hash: 5a9080592de3f5f4912d4d373466c33d096886f7c080961bccb46037e1c3f79e
Tx public key: 56d8bc1218463edfde3746f59a7e548ddc9a129da426e696fdd7a8c79d081299
Timestamp: 1710707718 Timestamp [UCT]: 2024-03-17 20:35:18 Age [y:d:h:m:s]: 01:010:09:39:41
Block: 980537 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 268395 RingCT/type: yes/0
Extra: 0156d8bc1218463edfde3746f59a7e548ddc9a129da426e696fdd7a8c79d0812990211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1be3d749d87a298e0d40c95a923ce663e76cb329d647ed8cec3db2c3ed4ca6ad 0.600000000000 1440612 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": 980547, "vin": [ { "gen": { "height": 980537 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1be3d749d87a298e0d40c95a923ce663e76cb329d647ed8cec3db2c3ed4ca6ad" } } ], "extra": [ 1, 86, 216, 188, 18, 24, 70, 62, 223, 222, 55, 70, 245, 154, 126, 84, 141, 220, 154, 18, 157, 164, 38, 230, 150, 253, 215, 168, 199, 157, 8, 18, 153, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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