Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 45f670399f3e187b54569a1bd5bdd2f0c3a7b363523943e680ff240d3391a776

Tx prefix hash: a38322cb27c4ca27dde2daede0e0ed8e1c8d5987df22bb15e3d2d5f3c78c6b49
Tx public key: d477a3d2adc0bf4c33dff227b3e639d05c93a4b04e68b9f4ccf8e39173ea8c2d
Timestamp: 1719863859 Timestamp [UCT]: 2024-07-01 19:57:39 Age [y:d:h:m:s]: 00:300:19:10:42
Block: 1056419 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214960 RingCT/type: yes/0
Extra: 01d477a3d2adc0bf4c33dff227b3e639d05c93a4b04e68b9f4ccf8e39173ea8c2d02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d4c69c3276e01825d2e71887082248fe9af1879eac43b94d4b1eb47df529ce55 0.600000000000 1526832 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": 1056429, "vin": [ { "gen": { "height": 1056419 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d4c69c3276e01825d2e71887082248fe9af1879eac43b94d4b1eb47df529ce55" } } ], "extra": [ 1, 212, 119, 163, 210, 173, 192, 191, 76, 51, 223, 242, 39, 179, 230, 57, 208, 92, 147, 164, 176, 78, 104, 185, 244, 204, 248, 227, 145, 115, 234, 140, 45, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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