Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 667185cc6dbbae3e7b88c2ec13ef21f64536fbd7dd2be23ca88bdcda25bd56fe

Tx prefix hash: bf0ed9d350ad67d399ab209cee41c7e08b2bb4fbc167eaf81802f11f8bbbf16e
Tx public key: 5e0c8a40ce651d520cbb87e589e36413c872d85f9680d9ab7b5c0179f1118a5d
Timestamp: 1724894314 Timestamp [UCT]: 2024-08-29 01:18:34 Age [y:d:h:m:s]: 00:218:09:29:55
Block: 1098132 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 155941 RingCT/type: yes/0
Extra: 015e0c8a40ce651d520cbb87e589e36413c872d85f9680d9ab7b5c0179f1118a5d02110000000a91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c6c48498fd9067001788fd49d55b62172042b8c6065d22e5be2721ac689cdc44 0.600000000000 1573743 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": 1098142, "vin": [ { "gen": { "height": 1098132 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c6c48498fd9067001788fd49d55b62172042b8c6065d22e5be2721ac689cdc44" } } ], "extra": [ 1, 94, 12, 138, 64, 206, 101, 29, 82, 12, 187, 135, 229, 137, 227, 100, 19, 200, 114, 216, 95, 150, 128, 217, 171, 123, 92, 1, 121, 241, 17, 138, 93, 2, 17, 0, 0, 0, 10, 145, 225, 60, 4, 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