Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66163b7c734bd0bf16948dec791a0ccdbcc15a733d7d6fc9825c28a0c5aaa739

Tx prefix hash: 7c89399b433cde5912622f9b9d6fefc7c293ab6e607509412c9ed2ee1e73f362
Tx public key: 13d52de9c3c8d7200d270a06da2137abd3ce9a6fd5882a025cfe71e44915ed05
Timestamp: 1728564809 Timestamp [UCT]: 2024-10-10 12:53:29 Age [y:d:h:m:s]: 00:169:17:58:55
Block: 1128555 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121109 RingCT/type: yes/0
Extra: 0113d52de9c3c8d7200d270a06da2137abd3ce9a6fd5882a025cfe71e44915ed0502110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a3d5b8d8d70e5092d4a39dca9588e33fd7837a49973c39e749aef0a483da9693 0.600000000000 1611374 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": 1128565, "vin": [ { "gen": { "height": 1128555 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a3d5b8d8d70e5092d4a39dca9588e33fd7837a49973c39e749aef0a483da9693" } } ], "extra": [ 1, 19, 213, 45, 233, 195, 200, 215, 32, 13, 39, 10, 6, 218, 33, 55, 171, 211, 206, 154, 111, 213, 136, 42, 2, 92, 254, 113, 228, 73, 21, 237, 5, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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