Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e75b5d564a9d278cfbdba104aa4d61d15805a8ac52abd4d210ba37beac4a699

Tx prefix hash: db3a1007d8fc8003a868ea7f6703fcd3f61a072ef6769d1e3362e6f14338bd7c
Tx public key: 8d551d2cf32181f39eb0290cc029465ea179b80f983ca4aecc24514baa541574
Timestamp: 1732874062 Timestamp [UCT]: 2024-11-29 09:54:22 Age [y:d:h:m:s]: 00:123:18:21:09
Block: 1164192 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 88246 RingCT/type: yes/0
Extra: 018d551d2cf32181f39eb0290cc029465ea179b80f983ca4aecc24514baa5415740211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6d7adb46f7ea31a5360afe6568f7dc332a9c5f1ec12cdfd4ad44c828f07a9f26 0.600000000000 1649865 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": 1164202, "vin": [ { "gen": { "height": 1164192 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6d7adb46f7ea31a5360afe6568f7dc332a9c5f1ec12cdfd4ad44c828f07a9f26" } } ], "extra": [ 1, 141, 85, 29, 44, 243, 33, 129, 243, 158, 176, 41, 12, 192, 41, 70, 94, 161, 121, 184, 15, 152, 60, 164, 174, 204, 36, 81, 75, 170, 84, 21, 116, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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