Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 131a10c2be2c485529c089e83effe8538264399059106b4b89378d440d2c3156

Tx prefix hash: 48663722b41426098cc5b4b8b6afad1997a02a34b4c4430309a6321aa9fa8544
Tx public key: d28c864c95a16e7ae3628c712e683d149a5bab0c4f4ff733e47b132e4a811ed6
Timestamp: 1677148490 Timestamp [UCT]: 2023-02-23 10:34:50 Age [y:d:h:m:s]: 02:054:23:38:03
Block: 703174 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 560900 RingCT/type: yes/0
Extra: 01d28c864c95a16e7ae3628c712e683d149a5bab0c4f4ff733e47b132e4a811ed602110000000174b6d784000000000000000000

1 output(s) for total of 2.871392391000 dcy

stealth address amount amount idx
00: 546dff2d7e2dcd25dd7c5a49a775d6d08e400a9c0069db607aa128968310b110 2.871392391000 1146743 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": 703184, "vin": [ { "gen": { "height": 703174 } } ], "vout": [ { "amount": 2871392391, "target": { "key": "546dff2d7e2dcd25dd7c5a49a775d6d08e400a9c0069db607aa128968310b110" } } ], "extra": [ 1, 210, 140, 134, 76, 149, 161, 110, 122, 227, 98, 140, 113, 46, 104, 61, 20, 154, 91, 171, 12, 79, 79, 247, 51, 228, 123, 19, 46, 74, 129, 30, 214, 2, 17, 0, 0, 0, 1, 116, 182, 215, 132, 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