Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2bcbe8a28d5f3da114326ca5347e0f7da585bf3c6dcd89f69764ab3ebea34c6d

Tx prefix hash: e632b68af071cf3ada10476c39a9d8a89c979c329f14a5e6187b7b0024ff0053
Tx public key: 8e7cdbd23256d72cbc3accaeec436a4103447ea175e5aad6e6fd16449df5c29a
Timestamp: 1733689493 Timestamp [UCT]: 2024-12-08 20:24:53 Age [y:d:h:m:s]: 00:103:06:50:47
Block: 1170967 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 73589 RingCT/type: yes/0
Extra: 018e7cdbd23256d72cbc3accaeec436a4103447ea175e5aad6e6fd16449df5c29a02110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3bcf754ff79c891d26daf01d93491362c58050d1c3a90954215e6b7def8d276f 0.600000000000 1656702 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": 1170977, "vin": [ { "gen": { "height": 1170967 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3bcf754ff79c891d26daf01d93491362c58050d1c3a90954215e6b7def8d276f" } } ], "extra": [ 1, 142, 124, 219, 210, 50, 86, 215, 44, 188, 58, 204, 174, 236, 67, 106, 65, 3, 68, 126, 161, 117, 229, 170, 214, 230, 253, 22, 68, 157, 245, 194, 154, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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