Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ac62ade3a435dbbd78d9a4df1ad3c658116513e953e9d09e54ca65aaa8341e4

Tx prefix hash: 4a5d693cee32208a54d818e467a863bd3a6570cb3d18adcd3e81849882ba850a
Tx public key: 7738d7133bd648c539039b1d23e0f6f2ce1cfa9847d4b8c00c206dca27cb3e09
Timestamp: 1637595087 Timestamp [UCT]: 2021-11-22 15:31:27 Age [y:d:h:m:s]: 03:113:00:33:56
Block: 379763 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 859470 RingCT/type: yes/0
Extra: 017738d7133bd648c539039b1d23e0f6f2ce1cfa9847d4b8c00c206dca27cb3e09021100000002137be99f000000000000000000

1 output(s) for total of 33.860074939000 dcy

stealth address amount amount idx
00: 2308b86ad2f0f1b7e0e0cf63725ce1e61dffd691ce21ea0ccb8b5d0d23b92269 33.860074939000 767539 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": 379773, "vin": [ { "gen": { "height": 379763 } } ], "vout": [ { "amount": 33860074939, "target": { "key": "2308b86ad2f0f1b7e0e0cf63725ce1e61dffd691ce21ea0ccb8b5d0d23b92269" } } ], "extra": [ 1, 119, 56, 215, 19, 59, 214, 72, 197, 57, 3, 155, 29, 35, 224, 246, 242, 206, 28, 250, 152, 71, 212, 184, 192, 12, 32, 109, 202, 39, 203, 62, 9, 2, 17, 0, 0, 0, 2, 19, 123, 233, 159, 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