Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c8c17c796f57be302f7d856fdedba9b6ad7cc7c50b84ac5f11e3cd76c178e69e

Tx prefix hash: 61544fb105a3b9730d41ca5197a2a7faf52bd34afa3c1e33ad638e6a8afc3090
Tx public key: 58f8179be71add8ceeabf9095354ebd8044d42b57c1b856e671081a01e54dc03
Timestamp: 1695339603 Timestamp [UCT]: 2023-09-21 23:40:03 Age [y:d:h:m:s]: 01:203:00:20:29
Block: 853300 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 406178 RingCT/type: yes/0
Extra: 0158f8179be71add8ceeabf9095354ebd8044d42b57c1b856e671081a01e54dc03021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.913404044000 dcy

stealth address amount amount idx
00: 50a9b6e9f83b7c15fb7f988deb4e0b583efa2ca312ecc9cb8b2acabee148acb8 0.913404044000 1307200 of 0

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": 853310, "vin": [ { "gen": { "height": 853300 } } ], "vout": [ { "amount": 913404044, "target": { "key": "50a9b6e9f83b7c15fb7f988deb4e0b583efa2ca312ecc9cb8b2acabee148acb8" } } ], "extra": [ 1, 88, 248, 23, 155, 231, 26, 221, 140, 238, 171, 249, 9, 83, 84, 235, 216, 4, 77, 66, 181, 124, 27, 133, 110, 103, 16, 129, 160, 30, 84, 220, 3, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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