Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 37a018364a0be8b5d1c69524e2c8d1cf7eb5eaca0ab135378c9df6b0db7c091e

Tx prefix hash: 99468f7f50babcdf751728716224f996b54cbf5d5af83fded85f5579645c0daf
Tx public key: cc6867ddfb0723f9be92f189d1bb18b8108a8b61eada5431926a017f9bbdfc69
Timestamp: 1735846971 Timestamp [UCT]: 2025-01-02 19:42:51 Age [y:d:h:m:s]: 00:279:17:04:56
Block: 1188802 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197367 RingCT/type: yes/0
Extra: 01cc6867ddfb0723f9be92f189d1bb18b8108a8b61eada5431926a017f9bbdfc69021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 683c60e829b4d726135b47f6c08a4c40b0e56a9a4b864ee95f292a45cb9cfe9d 0.600000000000 1675305 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": 1188812, "vin": [ { "gen": { "height": 1188802 } } ], "vout": [ { "amount": 600000000, "target": { "key": "683c60e829b4d726135b47f6c08a4c40b0e56a9a4b864ee95f292a45cb9cfe9d" } } ], "extra": [ 1, 204, 104, 103, 221, 251, 7, 35, 249, 190, 146, 241, 137, 209, 187, 24, 184, 16, 138, 139, 97, 234, 218, 84, 49, 146, 106, 1, 127, 155, 189, 252, 105, 2, 17, 0, 0, 0, 5, 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