Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 88b3572a5fe7860cb683c11db1aad7b06daec54b8c27f2c5f9a49ef6e81bbd13

Tx prefix hash: ca907b12eb497d6544b1eb4b34bcf49f4581932996591f33045bdf0915a1393c
Tx public key: 0f751782de7c93b039669dfdce71025095d6115bc40c4876fd95fc87af9f199a
Timestamp: 1705450060 Timestamp [UCT]: 2024-01-17 00:07:40 Age [y:d:h:m:s]: 01:100:04:14:04
Block: 936904 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332712 RingCT/type: yes/0
Extra: 010f751782de7c93b039669dfdce71025095d6115bc40c4876fd95fc87af9f199a0211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bfc607694d8cb197e2b9512644e606ab4405c8c71662a4cb2d07ef6f64e5b3ed 0.600000000000 1394946 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": 936914, "vin": [ { "gen": { "height": 936904 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bfc607694d8cb197e2b9512644e606ab4405c8c71662a4cb2d07ef6f64e5b3ed" } } ], "extra": [ 1, 15, 117, 23, 130, 222, 124, 147, 176, 57, 102, 157, 253, 206, 113, 2, 80, 149, 214, 17, 91, 196, 12, 72, 118, 253, 149, 252, 135, 175, 159, 25, 154, 2, 17, 0, 0, 0, 8, 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