Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c053e7a35b8a2106e1b54bff0366fcb7053a3bffd75586fe2319e0bb8214916

Tx prefix hash: 7754f89edd623c7d3ffb77ba59db003e1f6db5d18b867f762e80be2cb76ead13
Tx public key: f3e087ea98a0eb84133520b01336bb0c51ec09e89e86b9796b2ca7e5a3c3baca
Timestamp: 1715454437 Timestamp [UCT]: 2024-05-11 19:07:17 Age [y:d:h:m:s]: 01:033:09:28:46
Block: 1019899 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 284708 RingCT/type: yes/0
Extra: 01f3e087ea98a0eb84133520b01336bb0c51ec09e89e86b9796b2ca7e5a3c3baca02110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a21ff214cb0f10585c69e142faf1cc65fc3b3ea8366820684dc60820c28d6915 0.600000000000 1483952 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": 1019909, "vin": [ { "gen": { "height": 1019899 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a21ff214cb0f10585c69e142faf1cc65fc3b3ea8366820684dc60820c28d6915" } } ], "extra": [ 1, 243, 224, 135, 234, 152, 160, 235, 132, 19, 53, 32, 176, 19, 54, 187, 12, 81, 236, 9, 232, 158, 134, 185, 121, 107, 44, 167, 229, 163, 195, 186, 202, 2, 17, 0, 0, 0, 8, 89, 218, 211, 245, 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