Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3a4234382d3e60c8636e3ac6551a6feb6af0e5cab8475c320581a3fa8a52f22

Tx prefix hash: f160758338deb4b4699cc28d7dee7810a25678a0fa3f8814f0aa1696125043b3
Tx public key: cb7897a8cf34b5a85459b4ae81983eae98f592e65d2a3ff6538294a8c5592cfa
Timestamp: 1732341090 Timestamp [UCT]: 2024-11-23 05:51:30 Age [y:d:h:m:s]: 00:001:02:01:36
Block: 1159763 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 787 RingCT/type: yes/0
Extra: 01cb7897a8cf34b5a85459b4ae81983eae98f592e65d2a3ff6538294a8c5592cfa021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 528ba6867fc0ffdb0dd14712fc1b18afd7c4c92eb62f4853bfa855debd771b22 0.600000000000 1645402 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": 1159773, "vin": [ { "gen": { "height": 1159763 } } ], "vout": [ { "amount": 600000000, "target": { "key": "528ba6867fc0ffdb0dd14712fc1b18afd7c4c92eb62f4853bfa855debd771b22" } } ], "extra": [ 1, 203, 120, 151, 168, 207, 52, 181, 168, 84, 89, 180, 174, 129, 152, 62, 174, 152, 245, 146, 230, 93, 42, 63, 246, 83, 130, 148, 168, 197, 89, 44, 250, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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