Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 70b191238edb2762e2be62b92ccf243ed8ded2b32b84893f92d99f3d891889d6

Tx prefix hash: 275a0bb30860c447dd1c8791f532f69b4cb1db9fe3437364f6e294b2a7a868f2
Tx public key: 774d75ee6577378eea3b356ae11468a97b139c05ec5c66d68c20606cafff8437
Timestamp: 1709412592 Timestamp [UCT]: 2024-03-02 20:49:52 Age [y:d:h:m:s]: 01:031:05:56:41
Block: 969787 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 283324 RingCT/type: yes/0
Extra: 01774d75ee6577378eea3b356ae11468a97b139c05ec5c66d68c20606cafff843702110000000952d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 86c99c27a7b4d9a0a6d46c91dba038bb9a09b9b0e40fdc2752cf95236abc951c 0.600000000000 1429632 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": 969797, "vin": [ { "gen": { "height": 969787 } } ], "vout": [ { "amount": 600000000, "target": { "key": "86c99c27a7b4d9a0a6d46c91dba038bb9a09b9b0e40fdc2752cf95236abc951c" } } ], "extra": [ 1, 119, 77, 117, 238, 101, 119, 55, 142, 234, 59, 53, 106, 225, 20, 104, 169, 123, 19, 156, 5, 236, 92, 102, 214, 140, 32, 96, 108, 175, 255, 132, 55, 2, 17, 0, 0, 0, 9, 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