Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1af02d72818a2415f28c1d9bc67d55116cd8e98ce425ceba99f0cc208d1700b

Tx prefix hash: f66b6d944cae4903abcc8c61dd023ff39a87a0f82a8cfe71816c444a51a66014
Tx public key: 046cf66fd48d48a492e325e65d865100c16f2f046625cf7e9a2eddfb47ea09fd
Timestamp: 1731875916 Timestamp [UCT]: 2024-11-17 20:38:36 Age [y:d:h:m:s]: 00:188:22:30:03
Block: 1155929 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 134884 RingCT/type: yes/0
Extra: 01046cf66fd48d48a492e325e65d865100c16f2f046625cf7e9a2eddfb47ea09fd021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5737c5ebeafce4db35d6ff0a1db472fde07e15dc2c35156060071ba4fd5c330b 0.600000000000 1641548 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": 1155939, "vin": [ { "gen": { "height": 1155929 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5737c5ebeafce4db35d6ff0a1db472fde07e15dc2c35156060071ba4fd5c330b" } } ], "extra": [ 1, 4, 108, 246, 111, 212, 141, 72, 164, 146, 227, 37, 230, 93, 134, 81, 0, 193, 111, 47, 4, 102, 37, 207, 126, 154, 46, 221, 251, 71, 234, 9, 253, 2, 17, 0, 0, 0, 2, 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