Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f02b35c01598defa67baa07847e3fe22af2641213d6850764210b83751a2c5cd

Tx prefix hash: b95dbe41accabe44e19ffc4416cb0c1e5e53e55c77a3b7f0583352e0b4b6dae2
Tx public key: 612237a218306303ba4ea16a8aa2c81cd9623e737bd0fe3de7961e8b4fea3090
Timestamp: 1736975140 Timestamp [UCT]: 2025-01-15 21:05:40 Age [y:d:h:m:s]: 00:153:20:07:04
Block: 1198134 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109658 RingCT/type: yes/0
Extra: 01612237a218306303ba4ea16a8aa2c81cd9623e737bd0fe3de7961e8b4fea3090021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f3fb77df6266276b296079c215b347b0c28bf395c7dae50d08440117e8ae8c72 0.600000000000 1684753 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": 1198144, "vin": [ { "gen": { "height": 1198134 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f3fb77df6266276b296079c215b347b0c28bf395c7dae50d08440117e8ae8c72" } } ], "extra": [ 1, 97, 34, 55, 162, 24, 48, 99, 3, 186, 78, 161, 106, 138, 162, 200, 28, 217, 98, 62, 115, 123, 208, 254, 61, 231, 150, 30, 139, 79, 234, 48, 144, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 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