Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 171ee4aa45ee7cc212b75dbd3d8c6b650f1a4112e52af240aaef8dd026668c06

Tx prefix hash: 095688aa8158166df1651d5b6b2a394ee86e8c77fa6b086a28bba78cc03fc20c
Tx public key: f8900f2de2afa09ff0a48c60749f3785c1b13ccfbb0d2d0e17929e89b1377c23
Timestamp: 1709021836 Timestamp [UCT]: 2024-02-27 08:17:16 Age [y:d:h:m:s]: 00:344:19:22:46
Block: 966549 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 246542 RingCT/type: yes/0
Extra: 01f8900f2de2afa09ff0a48c60749f3785c1b13ccfbb0d2d0e17929e89b1377c2302110000000152d47e94000000000000000000

1 output(s) for total of 0.600040000000 dcy

stealth address amount amount idx
00: 7b026e5bb24055fbf538770ee002fe89e625d07a4ac1c3a75797dd45c24c9b90 0.600040000000 1426310 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": 966559, "vin": [ { "gen": { "height": 966549 } } ], "vout": [ { "amount": 600040000, "target": { "key": "7b026e5bb24055fbf538770ee002fe89e625d07a4ac1c3a75797dd45c24c9b90" } } ], "extra": [ 1, 248, 144, 15, 45, 226, 175, 160, 159, 240, 164, 140, 96, 116, 159, 55, 133, 193, 177, 60, 207, 187, 13, 45, 14, 23, 146, 158, 137, 177, 55, 124, 35, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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