Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff76ac9678a22922689e6bff1c6c711b0a80cbcf932a1bbe5c6539e6bf21b5c1

Tx prefix hash: 0f870d0f3271402cf78f74ce62bfdfdb66c5b8fac2ae451e75ac49c8b0b326b0
Tx public key: 53921e68e9ae7c707f6b93e5b867bcce9fec6f3f9496f4d5a04e9170c9f9786e
Timestamp: 1730357834 Timestamp [UCT]: 2024-10-31 06:57:14 Age [y:d:h:m:s]: 00:155:18:39:27
Block: 1143351 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111160 RingCT/type: yes/0
Extra: 0153921e68e9ae7c707f6b93e5b867bcce9fec6f3f9496f4d5a04e9170c9f9786e0211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e84ddfe5ac2b9346d92b73d64fcf8d4a627f4d66956bb800b047ada248859d0 0.600000000000 1627214 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": 1143361, "vin": [ { "gen": { "height": 1143351 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e84ddfe5ac2b9346d92b73d64fcf8d4a627f4d66956bb800b047ada248859d0" } } ], "extra": [ 1, 83, 146, 30, 104, 233, 174, 124, 112, 127, 107, 147, 229, 184, 103, 188, 206, 159, 236, 111, 63, 148, 150, 244, 213, 160, 78, 145, 112, 201, 249, 120, 110, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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