Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 100511c82fea1e9924f2ee2d00d3838f1f3067576705f654b45698383db1d5d1

Tx prefix hash: 93182e29cc0307b36f7d2ef9b73aa534b7ed5626b3cdae53323a766c601814b8
Tx public key: 06030343fd5d6fd71049839fa9af3bb512f2f0e29927ed49768e424fa47f3d57
Timestamp: 1735920615 Timestamp [UCT]: 2025-01-03 16:10:15 Age [y:d:h:m:s]: 00:103:18:45:11
Block: 1189422 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73947 RingCT/type: yes/0
Extra: 0106030343fd5d6fd71049839fa9af3bb512f2f0e29927ed49768e424fa47f3d5702110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 753f6e6bbb8f7ea20d3b6da30c15eb0e8d5d5d33b9867136071d2c3d1e027d2b 0.600000000000 1675931 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": 1189432, "vin": [ { "gen": { "height": 1189422 } } ], "vout": [ { "amount": 600000000, "target": { "key": "753f6e6bbb8f7ea20d3b6da30c15eb0e8d5d5d33b9867136071d2c3d1e027d2b" } } ], "extra": [ 1, 6, 3, 3, 67, 253, 93, 111, 215, 16, 73, 131, 159, 169, 175, 59, 181, 18, 242, 240, 226, 153, 39, 237, 73, 118, 142, 66, 79, 164, 127, 61, 87, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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