Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8c7cc7f38d1e1459700f81d5f317a11741569d6d488871c26f5b81a0d13b43d4

Tx prefix hash: 9b170ba8b3c122352589f309750b7a65034da0138a69e32dd485870fe8b8fcf3
Tx public key: b65705f45ae06a01b5e5246773a0ade19f23ee82a2e953cefd1636094ff2e538
Timestamp: 1702539720 Timestamp [UCT]: 2023-12-14 07:42:00 Age [y:d:h:m:s]: 00:353:02:51:40
Block: 912798 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 252854 RingCT/type: yes/0
Extra: 01b65705f45ae06a01b5e5246773a0ade19f23ee82a2e953cefd1636094ff2e538021100000005faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b654567e5de6d423c571d99100dcfa01a269036833f61b0e2b5bee71a7497ae6 0.600000000000 1370034 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": 912808, "vin": [ { "gen": { "height": 912798 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b654567e5de6d423c571d99100dcfa01a269036833f61b0e2b5bee71a7497ae6" } } ], "extra": [ 1, 182, 87, 5, 244, 90, 224, 106, 1, 181, 229, 36, 103, 115, 160, 173, 225, 159, 35, 238, 130, 162, 233, 83, 206, 253, 22, 54, 9, 79, 242, 229, 56, 2, 17, 0, 0, 0, 5, 250, 243, 92, 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