Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 979ae0ec20b77ef108dfa120df6845d36276ba0f65f7032ac844b57036ebfc36

Tx prefix hash: a809300997580448fb6624649d6a3c28ae6d7eeec8c4ccf33e3a2aa0dbc9a2a9
Tx public key: 94f93abcbb4232087e3b50ece3e19de6b007a5ecca0fd393dc0b7620427e61d9
Timestamp: 1702901966 Timestamp [UCT]: 2023-12-18 12:19:26 Age [y:d:h:m:s]: 01:329:14:06:22
Block: 915796 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 494416 RingCT/type: yes/0
Extra: 0194f93abcbb4232087e3b50ece3e19de6b007a5ecca0fd393dc0b7620427e61d9021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c8436ebb879410e1eed871f5294be9b40c067bb70894d749e77adfacfb27b7f5 0.600000000000 1373228 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": 915806, "vin": [ { "gen": { "height": 915796 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c8436ebb879410e1eed871f5294be9b40c067bb70894d749e77adfacfb27b7f5" } } ], "extra": [ 1, 148, 249, 58, 188, 187, 66, 50, 8, 126, 59, 80, 236, 227, 225, 157, 230, 176, 7, 165, 236, 202, 15, 211, 147, 220, 11, 118, 32, 66, 126, 97, 217, 2, 17, 0, 0, 0, 3, 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